Systems and methods for managing an account

ABSTRACT

An account is managed using information read from a dual frequency transponder. Information stored on the dual frequency transponder can be read by a NFC-enabled device and by a UHF RFID reader. The information links, corresponds, or otherwise provides access to account information stored at a remote server. For example, a NFC-enabled device can read the information from the dual frequency transponder and use that information to enable instant and on-the-spot recharging of a toll account. In addition, a UHF RFID toll reader can scan information from the dual frequency transponder and use that information to debit toll charges from the correct toll account. The dual frequency transponder can be embedded in a license plate and read using a reader placed in the road. Additionally, the transponder can be configured to function at the correct frequency only when a valid vehicle registration sticker is applied to the license plate.

RELATED APPLICATION INFORMATION

This application is a Continuation of U.S. application Ser. No.15/167,829 filed on May 27, 2016, which is a Continuation of U.S. Ser.No. 14/459,299, filed on Aug. 13, 2014, now Issued U.S. Pat. No.9,355,398 which claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Patent Application No. 61/865,600, filed Aug. 13, 2013,which is incorporated herein by reference in its entirety as if setforth in full.

BACKGROUND 1. Technical Field

The embodiments described herein are related to radio frequencyidentification (RFID) applications, and more specifically toapplications that allow for improved management and recharging ofprepaid accounts.

2. Related Art

RFID is a technology that allows companies to develop applications in avariety of areas. At its core, RFID is a technology that allows for theidentification of objects or people and to communicate informationrelated to associated objects or people. Some of the major areas thatRFID is enabling new applications include asset tracking, companies canput RFID tags on assets that are lost or stolen often, that areunderutilized or that are just hard to locate at the time they areneeded; manufacturing, RFID has been used in manufacturing plants formore than a decade. It's used to track parts and work in process and toreduce defects, increase throughput and manage the production ofdifferent versions of the same product; supply chain management, RFIDtechnology has been used in closed loop supply chains or to automateparts of the supply chain within a company's control for years; paymentsystems, one of the most popular uses of RFID today is to pay for roadtolls without stopping; and security and access control, RFID has longbeen used as an electronic key to control who has access to officebuildings or areas within office buildings. There are also numerousother types of applications such as animal or human tracking andidentification, electronic passports, border crossing, libraryapplications,

An RFID system comprises one or more tags or transponders that aresomehow associated with an object or objects, and one or more readers orinterrogators configured to read information out of the tag. The readerreads information by broadcasting a Radio Frequency (RF) signal overcertain range. When a tag is within range of the reader and receives thesignal, it can reflect that signal back to the reader in order tocommunicate with the reader. In order to communicate, the reader may putcertain commands on the RF signal, and the tag can respond by puttinginformation stored in the tag onto the signal that is reflected back tothe reader.

RFID systems can employ various types of technology including activetechnology, semi-active technology and passive technology. Active andsemi-active systems include a battery within the tag. In passivesystems, no battery is included in the tag. Rather, the tag receives allthe energy it needs from the received RF signal. Because passive tags donot include a battery, they can be made smaller, are less expensive thanactive or semi-active tags, and can also provide much more flexibilityto design tags to meet various application and environmentalrequirements. While passive tags typically cannot communicate over aslong a distance, the size, cost, and flexibility provided by passivetags make them much more attractive for many applications.

RFID systems can also operate over many frequency ranges and inaccordance with several communication protocols. A couple of the mostcommon frequency ranges are the High Frequency (HF) band (13.56 MHz) andUltra-High Frequency (UHF) band (865-928 MHz). HF systems can operateover shorter ranges, e.g., 10 cm-1 m, and at lower data rates, whereasthe UHF systems can operate over longer ranges 1-12 m, and at higherdata rates.

Near Field Communication (NFC) systems are examples of HF systems. NFCis a set of standards for smartphones and similar devices to establishradio communication with each other by touching them together orbringing them into proximity, usually no more than a few inches. Presentand anticipated applications include contactless transactions, dataexchange, and simplified setup of more complex communications such asWi-Fi. Communication is also possible between an NFC device and anunpowered NFC chip in a tag.

NFC standards cover communications protocols and data exchange formats,and are based on existing radio-frequency identification standardsincluding ISO/IEC 14443 and FeliCa. The standards include ISO/IEC18092[4] and those defined by the NFC Forum, which was founded in 2004by Nokia, Philips and Sony, and now has more than 160 members. The Forumalso promotes NFC and certifies device compliance. It fits the criteriafor being considered a personal area network.

NFC builds upon RFID systems by allowing two-way communication betweenendpoints, where earlier systems such as contact-less smartcards wereone-way only. NFC devices can also be used in contactless paymentsystems, similar to those currently used in credit cards and electronicticket smartcards, and allow mobile payment to replace or supplementthese systems. For example, Google Wallet allows consumers to storecredit card and store loyalty card information in a virtual wallet andthen use an NFC-enabled device at terminals that accepts, for example,MasterCard PayPass transactions. The NFC Forum also promotes thepotential for NFC-enabled devices to act as electronic identitydocuments and keycards. As NFC has a shorter range and supportsencryption, it is generally better suited than earlier, less privateRFID systems for exchanging sensitive data such as personal finance andidentification.

While there are many uses for HF technologies such as NFC, UHFtechnologies typically support longer range communication and higherdata rates. Thus, UHF technology tends to excel in applications thatinclude but is not limited to tolling and electronic vehicleregistration, asset supervision, and supply chain management.

SUMMARY

A RFID system comprising a dual frequency RFID transponder.

These and other features, aspects, and embodiments are described belowin the section entitled “Detailed Description.”

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments are described in conjunction with theattached drawings, in which:

FIG. 1A illustrates a system for managing an account according tovarious embodiments;

FIG. 1B is a flowchart illustrating a process for managing an accountaccording to various embodiments;

FIG. 2 illustrates an embodiment of a process for managing an accountaccording to various embodiments;

FIG. 3 illustrates a system for managing an account according to variousembodiments;

FIG. 4 is a block diagram illustrating a transponder according tovarious embodiments;

FIG. 5 is a block diagram illustrating a UHF system according to variousembodiments;

FIG. 6 is a block diagram illustrating an HF system according to variousembodiments;

FIG. 7A illustrates the top view of an RFID-enabled license plateaccording to various embodiments;

FIG. 7B illustrates the top view of an RFID-enabled license plateaccording to various embodiments;

FIG. 7C illustrates the top view of an RFID-enabled license plateaccording to various embodiments;

FIG. 8 illustrates the top view of an RFID-enabled license plateaccording to various embodiments;

FIG. 9 illustrates a vehicle registration sticker according to variousembodiments; and

FIG. 10 illustrates an RFID reader according to various embodiments.

DETAILED DESCRIPTION

The embodiments disclosed herein can be implemented in numerous ways,including as a process; an apparatus; a system; a composition of matter;a computer program product embodied on a computer readable storagemedium; and/or a processor, such as a processor configured to executeinstructions stored on and/or provided by a memory coupled to theprocessor. In this specification, these example embodiments, or anyother implementations, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered. Unless statedotherwise, a component such as a processor or a memory described asbeing configured to perform a task may be implemented as a generalcomponent that is temporarily configured to perform the task at a giventime or a specific component that is manufactured to perform the task.As used herein, the term ‘processor’ refers to one or more devices,circuits, and/or processing cores configured to process data, such ascomputer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of operation. The invention is described in connection withsuch embodiments, but the invention is not limited to any embodiment.The scope of the invention is limited only by the claims and theinvention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Various embodiments of the systems and methods described herein aredirected toward applications for a multi-frequency transponder. Inparticular, the various embodiments of the systems and methods describedherein are directed toward applications for a dual frequency transponderthat incorporates both UHF and HF capabilities, and is therefore able tooperate over both the UHF band (e.g., 865-928 MHz) and the HF band(e.g., 13.56 MHz).

U.S. Provisional Patent Application Ser. No. 61/811,649, entitled‘Systems and Methods for Connecting People with Product Information,”filed Apr. 12, 2013, describes one application for a dual frequencytransponder. Meanwhile, the various embodiments of the systems andmethods described herein are directed toward applying the dual frequencytransponder to streamline electronic prepayment routines and practices.In particular, in various embodiments, a dual frequency transponder isused to enable immediate and on-the-spot prepayment of road tollsenforced through Electronic Toll Collection (ETC) systems. Althoughembodiments of the systems and methods described herein are with respectto applications for a dual frequency transponder in electronic tollcollection, it is to be understood that there are numerous otherpossible applications of a dual frequency transponder. For example,other applications for a dual frequency transponder include but are notlimited to parking access, customs and border control, and electronicvehicle registration (EVR).

ETC systems eliminate traffic delays on toll roads by automating tollcollection and obviating protracted stops at manual toll booths.Although a few ETC systems allows toll charges to be postpaid (i.e.,billed to users periodically and/or a later date), by far the mostcommon ETC billing mechanism is to automatically deduct the toll chargesfrom prepaid debit accounts. Generally, an ETC system must firstidentify a passing vehicle before it can electronically debit theaccount of registered vehicle owner. For vehicle identification, mostETC systems operating today (e.g., E-ZPass®) rely on RFID technology.More specifically, most ETC systems issue RFID transponders or tags thatare then registered or activated to link to specific vehicle owneraccounts. For instance, in order for a user, Alice, to gain access to anETC service, she will initially have to set up a toll account with anappropriate transit or toll authority (e.g., FasTrak® in the SanFrancisco Bay Area), and then carry a registered or activated RFIDtransponder in or on her vehicle. Meanwhile, most toll plazas have RFIDreader equipment installed on at least some toll gates. As Alice'svehicle passes through a toll gate on the San Francisco-Oakland BayBridge, the onboard FasTrak® transponder communicates to a RFID tollreader a unique radio signature identifying the vehicle. Based on thisunique radio signature, the ETC system can then determine the account(i.e., Alice's) from which to deduct the amount of the toll.

Some prepaid toll accounts are set up to be automatically replenishedwhenever the balance falls below a certain threshold. For example, ifAlice subscribes to a FasTrac® credit card account, a replenishmentamount equaling her average monthly usage (determined based on theprevious 90 days of use) is charged to the credit card linked to theaccount whenever the account's balance falls below a threshold of $15.Most users, however, want autonomy over their prepaid toll accountbalances and would prefer to recharge their prepaid toll account attheir own discretion. Control over when and how much to recharge a tollaccount is especially attractive to users who incur toll charges on aninfrequent, intermittent, or irregular basis.

Nevertheless, current technology still imposes drastic limitations onwhen and where users can recharge prepaid toll accounts. Generally,recharging can only be performed at designated Point of Sale (POS)stations (e.g., convenient store, ATM). As such, users are required totake a number of proactive measures (e.g., check toll account status orbalance, find a POS station) well in advance of crossing a toll roadsince recharging cannot be done instantaneously and on-the-spot. Inpractice, many users will fail to check their account balance beforehandand won't realize that their account balance is insufficient until theyare at or near a toll gate where, absent any POS stations, they mustthen resort to time consuming manual toll transactions.

One primary reason why current technology falls short is that theconventional toll transponders in use today are single frequencydevices. The E-ZPass® transponder, for instance, operate over only asingle UHF (i.e., 915 MHz) band. Conventional toll transponders aredesigned to communicate only with the UHF RFID readers at toll gates.Consequently, only UHF RFID toll readers can gain access to theinformation stored on conventional toll tags. In contrast, the variousembodiments of the systems and methods described herein are directedtoward a dual frequency transponder. In various embodiments, Near FieldCommunication (NFC) technology is integrated with a UHF transponder. Theresulting dual frequency transponder, in various embodiments, is capableof communicating with NFC-enabled devices as well as UHF RFID readers.In various embodiments, when implemented as a toll transponder for usein an ETC system, the dual frequency transponder can communicate withboth a user's NFC-enabled device (e.g., smartphone) and the typical UHFRFID reader equipment found at toll gates.

Since Nokia introduced the first NFC-enabled phone in 2006, a steadystream of phones with NFC capabilities (e.g., Samsung Nexus™, MotorolaDroid) have been marketed and sold. As a result, a growing number ofusers have a portable NFC reader constantly ready at their disposal. AnNFC-enabled smartphone is equipped with an embedded NFC reader modulethat can communicate with other NFC devices, including but not limitedto other NFC-enabled smartphones, NFC POS terminals, and NFCtransponders and tags. Unlike other wireless technologies such asBluetooth®, which generally require manual device discovery and/orpairing, two NFC devices can detect and automatically initiate aconnection with one another as soon as they are within range (e.g., 4 cmor less). For example, an unlocked Google Android® smartphone will scanfor NFC tags, analyze any discovered NFC tags, categorize data from theNFC tags, and then launch the appropriate application(s) to handle eachNFC tag.

Prepaid Account Recharging Solution

FIG. 1A illustrates a system 100 for managing an account according tovarious embodiments. Referring to FIG. 1A, the system 100 includes atransponder 110. In various embodiments, the transponder 110 is a dualfrequency transponder that communicates with a device 120 and a reader130 using different frequency bands. In some embodiments, thetransponder 110 is a dual frequency transponder that can operate overboth the HF and UHF band. As will be described in more detail below, insome embodiments, the transponder 110 can be embedded, integrated, orotherwise included in a vehicle license plate. However, it is to beunderstood that multiple other embodiments of the transponder 110 arepossible, including, for example, but not limited to, a sticker (e.g., aself-adhesive decal that can be placed on an automobile window,windshield, or license plate), a clamshell card, and an encapsulateddevice (e.g., in the housing of a rear-view mirror, headlights ortaillights, the vehicle's front or rear bumpers, or in anynon-conductive component of the vehicle). In some embodiments, thetransponder 110 may be an active or semi-active device that relies on abuilt-in power source (e.g., batteries) to transmit its signals. Inother embodiments, the transponder 110 may be a passive device thatcollects energy from interrogating signals from the device 120 and thereader 130.

As shown in FIG. 1A, in various embodiments, the transponder 110communicates with the device 120. In various embodiments, the device 120may be an NFC-enabled device (e.g., Android® smartphone) and thetransponder 110 may communicate with the device 120 using the HF band.Meanwhile, in various embodiments, the transponder 110 may alsocommunicate with the reader 130. In various embodiments, the reader 130may be a UHF RFID reader device and the transponder 110 may communicatewith the reader 130 using the UFH band. In particular, in variousembodiments, the reader 130 can be a type of RFID reader device that istypically installed at an electronic toll gate. However, as will bedescribed in more detail below, in embodiments where the transponder 110is integrated, embedded, or otherwise included in a license plate, thereader 130 may preferably be placed in the road, underneath passingvehicles as opposed to in an overhead gantry.

In various embodiments, the device 120 communicates with the transponder110 in order to manage a toll account, and to recharge the toll accountinstantaneously and on-the-spot. As shown in FIG. 1A, an application 121is installed on the device 120. In various embodiments, interactionsbetween the transponder 110 and the device 120 may trigger or activatethe application 121. For example, in one embodiment, touching or tappingthe transponder 110 and the device 120 together may launch theapplication 121 on the device 120. Alternately, in some embodiments, theapplication 121 may launch when the device 120 is brought within closeproximity of the transponder 110. In various embodiments, interactionsbetween the transponder 110 and the device 120 may further allow thedevice 120 to scan, read, or otherwise retrieve information stored onthe transponder 110. For example, in one embodiment, by touching,tapping, or otherwise positioning the transponder 110 and the device 120together, the device 120 may be able to read the information that isstored on the transponder 110. In various embodiments, the device 120may determine to launch the application 121 automatically based on atleast some of the information read from the transponder 110. In someembodiments, instead of gaining access to all of the information storedon the transponder 110 at once, interaction between the device 120 andthe transponder 110 may initiate an authentication process. In someembodiments, before the device 120 is able to access, for example,prepaid toll account information, a user may be required to provide theproper credentials (e.g., biometrics, username, password).

In various embodiments, at least some of the information stored on thetransponder 110 may identify, link, or otherwise provide access to acorresponding prepaid toll account. As will be described in more detailbelow, in various embodiments, the application 121 is able to use atleast some of the information read from the transponder 110 to obtaininformation associated with the toll account, including, for example,but not limited to, an account status and account balance. As shown inFIG. 1A, the application 121 may communicate with an ETC server 170 overa network 140. In various embodiments, the network 140 may comprise oneor more of a wired network, a wireless network, a local area network, awide area network, the Internet, or any other appropriate network. Insome embodiments, the application 121 may use web or applicationservices provided by the ETC server 170 in order to obtain prepaid tollaccount information (e.g., account status, account balance). Thus, insome embodiments, by activating the application 121 through interactionsbetween the transponder 110 and the device 120 (e.g., touch, tap), auser can gain immediate access to current prepaid toll accountinformation (e.g., status, balance).

In various embodiments, the application 121 may additionally provide auser interface for recharging a toll account. For instance, in someembodiments, the application 121 may provide one or more graphic userinterface (GUI) components (e.g., text areas or fields, radio buttons,checkboxes, drop-down menu) allowing a user to select or enter one ormore inputs including, for example, but not limited to, a rechargeamount, a payment method (e.g., a credit card selection), and securityor authentication credentials for the virtual wallet. In variousembodiments, the application 121 may be integrated with a virtual wallet(e.g., Google Wallet™) on the device 120. As will be described in moredetail below, in various embodiments, the application 121 may interactwith the virtual wallet (e.g., Google Wallet™) to replenish the user'sprepaid toll account.

As shown in FIG. 1A, in various embodiments, in addition to the ETCserver 170, the application 121 may also communicate with both anelectronic wallet (E-Wallet) server 150 and a payment processor server160 over the network 140. In some embodiments, the application 121 mayrequest payment information (e.g., a credit card number) from theE-Wallet server 150 so that the application 121 may then request paymentprocessor server 160 to submit an appropriate recharge amount to the ETCserver 170 replenishing the user's prepaid toll account. Advantageously,in various embodiments, a prepaid toll account may be managed andreplenished instantaneously and on-the-spot. For instance, in variousembodiments, a user is no longer required to seek out a POS station butcan instead recharge his or her prepaid toll account while on the roadand from inside the vehicle.

In various embodiments, the transponder 110 may also communicate withthe reader 130. In various embodiments, the reader 130 comprises a UHFRFID reader that is capable of reading information stored on thetransponder 110 using the UHF (865-928 MHz) band. As shown in FIG. 1A,in various embodiments, the reader 130 may be an RFID reader installedat a toll gate. Furthermore, as FIG. 1A shows, the reader 130 maycommunicate with the ETC server 170 over the network 140. In someembodiments, information that the reader 130 reads from the transponder110 may be transmitted to the ETC server 170 via the network 140. Aswill be described in more detail below, in various embodiments,information stored on the transponder 110 can link, correspond, orotherwise provide access to other information, such as information thatis stored elsewhere and remotely on a network server. For example, invarious embodiments, the ETC server 170 may use the information readfrom the transponder 110 to identify a vehicle and to apply a tollcharge to an account associated with the vehicle.

FIG. 1B is a flowchart illustrating a process 150 for managing accountaccording to various embodiments. In various embodiments, the process150 may be triggered as a result of interactions between the transponder110 and the device 120 described with respect to FIG. 1A.

At 152, at least some of the information stored on a dual-frequencytransponder is accessed. For example, as described with respect to FIG.1A, an NFC-enabled device such as the device 120 (e.g., Android®smartphone) is able to read the information stored on the transponder110. In some embodiments, at last some of the information read from thetransponder 110 may trigger the launch of the application 121 on thedevice 120. In addition, a UHF RFID toll reader such as the reader 130may also be able to read some or all of the information stored on thetransponder 110.

At 154, account information is accessed based on the information storedon the dual-frequency transponder. In various embodiments, at least someof the information stored on the transponder 110 may link, correspond,or otherwise provide access to account information. In variousembodiments, the information stored on the transponder 110 may link,correspond, or otherwise provide access to account information that isstored at a remote server (e.g., the ETC server 170). In someembodiments, the information stored at the remote server includesprepaid toll account information including, for example, but not limitedto, account status and account balance.

At 156, at least one action is performed with respect to the account.For example, in some embodiments, the action may include, for example,but not limited to, communicating the account information stored at theremote server (e.g., account status, account balance) to a user of thedevice 120 via the application 121. As another example a type of actionthat can be performed with respect to the account, the user of thedevice 120 may also use the application 121 to recharge the tollaccount. As will be described in more detail below, the user of thedevice 120 may replenish the toll account through a virtual wallet thatmay be integrated with the application 121. Finally, in someembodiments, a UHF RFID toll reader may also able to read theinformation stored on the transponder 110. In various embodiments, theUHF RFID toll reader can be configured to provide some or all of thisinformation to an ETC system (e.g., the ETC server 170). In variousembodiments, based on information scanned from the dual-frequencytransponder by the UHF RFID toll reader, the ETC system may be able todetermine the account from which to deduct a toll charge.

Recharging with a Virtual Wallet

As described earlier with respect to FIG. 1A, various embodiments of thesystems and methods described herein simplify and abbreviate the processto recharge a toll account. For instance, in various embodiments, therecharging process may be initiated by simply bringing an NFC-enableddevice (e.g., the device 120) within the range of a dual frequencytransponder (e.g., the transponder 110). In response, in variousembodiments, the NFC-enabled device (e.g., the device 120) may launch anapplication (e.g., the application 121) that is integrated with avirtual wallet (e.g., Google Wallet™). Otherwise stated, in variousembodiments, scanning a dual frequency toll transponder with anNFC-enabled device may trigger an application that is configured tointeract directly with a virtual wallet on the NFC-enabled device. Invarious embodiments, the application provides a user interface for auser to select or enter various inputs (e.g., amount, credit card,credentials) to recharge a toll account. At the same time, in variousembodiments, functions and features of the virtual wallet may beintegrated into the application using one or more appropriateApplication Programming Interfaces (APIs). For example, to enable theintegration of Google Wallet™ within the application, the Android®Software Development Kit (SDK) offers the following three basic APIs:Google Wallet online commerce API, Google Wallet for digital goods API,and Google Checkout API.

FIG. 2 illustrates an embodiment of a process 200 for recharging a tollaccount using a virtual wallet. In various embodiments, the process 200is performed by an application, such as the application 121 installed onthe device 120 described with respect to FIG. 1A. In some embodiments,the process 200 may implement operation 156 of the process 100 describedwith respect to FIG. 1B. In one exemplary embodiment, the process 200may be performed by an application to recharge a toll account usingpayment information obtained directly from Google Wallet™. In variousembodiments, the application may be configured to exchange paymentinformation with a Google Wallet™ backend server. In variousembodiments, the application and the Google Wallet™ backend serverexchange payment information using signed JavaScript Object Notation(JSON) data objects called JSON Web Tokens (JWTs).

In some embodiments, the application may offer users the option torecharge their prepaid toll account using Google Wallet™.Advantageously, in some embodiments, using a virtual wallet such asGoogle Wallet™ further expedites the recharging process since users areable to avoid manually inputting payment information (e.g., credit cardnumber, billing address, etc.). For example, in some embodiments, aftera user, Bob, indicates that he would like to recharge his prepaid tollaccount by adding $10 to the account, he can then select or click on a“Buy with Google” button to complete or finalize the rechargingtransaction almost instantaneously. In some embodiments, selecting topay with a virtual wallet such as by clicking on the “Buy with Google”button may trigger the process 200.

At 202, masked wallet information is requested. In various embodiments,the application sends to the Google Wallet™ backend server a maskedwallet request JWT. In various embodiments, masked wallet informationcomprises a Java object containing a masked or partially hidden versionof Bob's credit card number. In some embodiments, masked walletinformation can further include Bob's shipping address. At 204, a maskedwallet object is received. In various embodiments, in response to therequest from the application, the Google Wallet™ backend server returnsto the application a masked wallet response JWT. In various embodiments,the application can display an order review page or screen to Bob basedon the masked wallet information. At 206, a full wallet is requested. Invarious embodiments, after receiving the masked wallet object at 204,the application will then need full wallet information to complete Bob'sorder. As such, in some embodiments, the application then sends to theGoogle Wallet™ backend server a full wallet request JWT. At 208, fullwallet information is received. In various embodiments, the GoogleWallet™ backend server responds to the request by providing a fullwallet response JWT to the application. In various embodiments, the fullwallet information includes details of a single-use virtual credit cardfor the transaction. At 210, the single-use virtual credit card istransmitted. In various embodiments, the application passes thesingle-use virtual credit card provided by Google Wallet™ in the fullwallet to a merchant server (e.g., the payment processor server 160described with respect to FIG. 1A). At 212, transaction status isreceived. In various embodiments, the merchant server processes thepayment and notifies the application of the status of the transaction(e.g., success or failure). Finally, at 214, a status notificationobject is transmitted. In various embodiments, based on the statusnotification from the merchant server (e.g., success or failure), theapplication then creates and sends a transaction status JWT to theGoogle Wallet™ backend server. In addition, in various embodiments, theapplication displays a confirmation screen informing Bob that $10 hasbeen added to his prepaid toll account.

Dual frequency Transponder Data Links

PCT Application No. PCT/EP2012/001765, entitled “Method and Apparatusfor Providing and Managing Information Linked to RFID Data Storage Mediain a Network”, filed Apr. 25, 2012, which is incorporated herein byreference, describes the management of data that is linked to orotherwise associated with a RFID storage medium. The various embodimentsof the methods and systems described herein are directed toward using adual frequency transponder to manage and replenish a toll account. Inthe various embodiments described herein, the dual frequency transpondercan communicate with both a NFC-enabled device and a UHF RFID reader. Invarious embodiments, data stored on the dual frequency transponderlinks, corresponds, or otherwise provide access to a toll account. Thus,in various embodiments, both NFC-enabled devices (e.g., Android®smartphones) and UHF RFID readers (e.g., common types of toll readers)are able to read or scan information that is stored on the dualfrequency transponder and then perform a number of essential functionsbased on this information.

According to various embodiments, an account may be managed andrecharged instantly and on-the-spot. In various embodiments, bringing anNFC-enabled device (e.g., the device 120) within the range of a dualfrequency transponder (e.g., the transponder 110) automatically triggersthe launch of an application (e.g., the application 121) on theNFC-enabled device (e.g., the device 120). In various embodiments, theapplication can provide current prepaid toll account information (e.g.,account status, account balance). Furthermore, in various embodiments,the application may be integrated with a virtual wallet (e.g., GoogleWallet™) thereby enabling a user to recharge the toll account instantlyand on-the-spot. In the example described with respect to FIG. 2, Bobuses his Android® smartphone to scan a dual frequency transponder and issubsequently able to add $10 to his prepaid toll account.

In various embodiments, the information stored in the dual frequencytransponder links, corresponds, or otherwise provides access to anaccount. In various embodiments, an NFC-enabled device reads data thatis stored on an RFID data storage medium (e.g., a dual frequencytransponder) and then uses this data to access additional data that isstored at a remote server. For example, in various embodiments, readingor scanning the information stored in the dual frequency transponderenables the application to access a designated memory area at a remoteserver (e.g., the ETC server 170). In some embodiments, the applicationis then able to retrieve, for example, prepaid toll account informationfrom the remote server (e.g., the ETC server 170). Additionally, invarious embodiments, the application is also able to update toll accountinformation stored at the remote server, including, for example, but notlimited to, by submitting a recharge payment that alters the status orthe balance of the toll account.

FIG. 3 illustrates a system 300 for managing an account according tovarious embodiments. In various embodiments, a user 32 may operate adevice 12, which is a NFC-enabled device such as an Android® smartphone.In various embodiments, an application 9 may be an application thatpermits the user 32 to manage and replenish a toll account, including byproviding current account information (e.g., status, balance) andoptions to replenish the toll account. In various embodiments, thedevice 12 includes an NFC RFID reader 8 that is capable of reading datastored in an RFID storage medium 4. In various embodiments, the RFIDstorage medium 4 may be a dual frequency transponder such as thetransponder 110 described with respect to FIG. 1A. In some embodiments,the application 9 is installed on the device 12. As such, in someembodiments, when the NFC UM reader 8 reads or scans data from the RFIDstorage medium 4, the device 12 may launch the application 9automatically based on this data. Otherwise stated, in some embodiments,the application 9 may be launched when the user 32 brings the device 12within sufficient range of the RFID storage medium 4 for the NFC RFIDreader 8 to read or scan data from the RFID storage medium 4. In otherembodiments, the application 9 may not be already installed on thedevice 12. In those embodiments, data read or scanned from the RFIDstorage medium 4 may direct the device 12 to a link to download andinstall the application 9.

As shown in FIG. 3, in various embodiments, the MD storage medium 4 mayinclude an RFID data record 24 and an additional memory 34. In variousembodiments, the NFC RFID reader 8 may be configured to read or scan thedata stored on the RFID data record 24. For example, in sonicembodiments, the NFC RFID reader 8 may direct a request to the RFIDstorage medium 4. In response, in some embodiments, the RFID storagemedium 4 may release data stored on the RFID data record 24 to the NFCUM reader 8. In some embodiments, the user 32 may be authenticated(e.g., biometrics, username, password) before the MD storage medium 4releases its data to the NFC RFID reader 8. In various embodiments, theapplication 9 may use the data released from the RFID data record 24 togenerate access rights for additional data 22 stored in data memory area20 of a remote server 18. In some embodiments, in order to generateaccess rights to the additional data 22, the user 32 may be required toprovide one or more forms of security or authentication credentials(e.g., biometrics, username, password). In one exemplary embodiment, theremote server 18 may be a server associated with an ETC system (e.g.,the ETC server 170) and the additional data 22 may include accountinformation (e.g., account status, account balance) with respect to atoll account associated with the user 32. In various embodiments, theapplication 9 requests for the additional data 22 from the remote server18 by sending, for example, access rights to the remote server 18 over anetwork 16. In various embodiments, in response to the request from theapplication 30, the remote server 18 may transmit the additional data 22to the device 12 via the network 16. In various embodiments, theapplication 9 can then provide, with or without further processing oranalysis, the additional data 22 to the user 32.

Dual Frequency Transponder

FIG. 4 is a block diagram illustrating a transponder 400 according tovarious embodiments. Referring to FIGS. 1A, 3, and 4, the transponder400 may implement the transponder 110 described with respect to FIG. 1Aand the RFID storage medium 4 described with respect to FIG. 3.

In various embodiments, the transponder 400 may be a multi-frequency orfrequency-independent transponder. In various embodiments, thetransponder 400 is a dual frequency transponder that operates over boththe HF (e.g., 13.56 MHz) and UHF (e.g., 865-928 MHz) band.Advantageously, in various embodiments, the transponder 400 is capableof communicating with both an NFC-enabled device and a UHF RFID reader.For instance, in some embodiments, when an NFC-enabled device such as anAndroid® smartphone is brought within the range of the transponder 400,the NFC-enabled device can respond by automatically launching anapplication (e.g., the application 121 described with respect to FIG. 1Aor the application 9 described with respect to FIG. 3) that enables aquick and on-the-spot recharge of a toll account. In addition, in someembodiments, a UHF RFID reader installed at a toll gate can useinformation scanned from the transponder 400 to determine the correctprepaid toll account from which to deduct a toll charge.

In various embodiments, the transponder 400 may include a base layer andat least one radio frequency device disposed upon the base layer. Invarious embodiments, the radio frequency device comprises at least onechip and at least one antenna that are in electrically coupled with thechip. In some embodiments, the transponder 400 can include afrequency-independent chip. In those embodiments, the transponder 400can include a single manufactured silicon chip that is configured,through proper connections and match to an appropriate antenna, tooperate using any of the relevant frequencies (e.g., 13.56 MHz and 915MHz) assigned to the transponder 400. Alternately, in some embodiments,the transponder 400 may include a multi-frequency (e.g., dual frequency)chip. In those embodiments, the transponder 400 may include a chip thatis designed and characterized to operate with a specific antenna atseveral (e.g., two) different frequencies.

As shown in FIG. 4, in some embodiments, the transponder 400 may includean analog control unit 410, which is a dual interface with a combinationof two frequencies. For example, in some embodiment, the analog controlunit 410 may include an HF (e.g., 13.56 MHz) system 411 and a UHF (e.g.,915 MHz) system 412, both described in more detail below. In variousembodiments, the UHF system 412 may operate over the 915 MHz band and isused for communicating with UHF RFID readers, including but not limitedto conventional UHF RFID toll readers. In some embodiment, the UHFsystem 412 may include a first antenna 413, which can be a dipoleantenna.

Meanwhile, in various embodiments, the HF system 411 may operate overthe 13.56 MHz band and is used for communicating with NFC-enableddevices, such as Android® smartphones. In some embodiments, the HFsystem 411 may include second antenna 414, which can be a coil antennaconstructed from a helix of insulated wire.

In various embodiments, the transponder 400 can further include adigital control unit 420 and a memory 430. In various embodiments, theanalog control unit 410 comprises a continuous-time system. That is, invarious embodiments, the analog control unit 410 comprises a system thatis continuous in both time and magnitude. Furthermore, in variousembodiments, the analog control unit 410 may be configured to input andoutput analog signals. A signal is considered analog if it is definedfor every point in time (i.e., continuous-time) and is able to take anyreal magnitude value within its range.

In contrast, in various embodiments, the digital control unit 420comprises a discrete-time and quantized system. In various embodiments,the digital control unit 420 may accept digital input signals andproduce digital output signals. A digital signal is only defined forparticular points in time (i.e., discrete-time) and can only take oncertain quantized values (e.g., 0s and 1s in a binary system). In someembodiments, the analog control unit 410, the digital control unit 420,and the memory 430 may all be components on a single integrated RFIDcircuit chip.

FIG. 5 is a block diagram illustrating the UHF system 412 according tovarious embodiments. In various embodiments, in various embodiments, theUHF system 412 may be used to implement the UHF component of a dualfrequency transponder, such as the transponder 110 described withrespect to FIG. 1A and the RFID storage medium 4 of described withrespect to FIG. 3. In various embodiments, the UHF system 412 operatesover a UHF (865-928 MHz) band. As shown in FIG. 5, the UHF system 412may use the 915 MHz or 2.45 GHz band. In various embodiments, a dualfrequency transponder that incorporates the UHF system 412 is capable isinteracting with a UHF RFID reader.

Many ETC systems have UHF RFID readers installed at toll gates. Forinstance, readers in the E-ZPass® system broadcast a 915 MHz signalwhile E-ZPass® transponders are configured to listen for and respond tothe 915 MHz signal. In some cases, particularly where a transponder isconfigured to operate passively, the transponder can respond to the 915MHz signal broadcast by a reader with a backscatter signal to the readerthat conveys the data stored in the transponder. In various embodiments,data transmitted to the UHF RFID reader includes data (e.g., a uniqueradio signature) that links, corresponds, or otherwise provides accessto the toll account associated with each passing vehicle. As such, invarious embodiments, this data enables the ETC system to identify ordetermine the toll account to which to apply the toll charge.

As shown in FIG. 5, the UHF system 412 may include an alternatingcurrent/direct current (AC/DC) converter 510, a power supply controlunit 520, an instruction sequencer 530, and a memory 540. In variousembodiments, the AC/DC converter 510 may receive and convert analternating current signal to a direct current signal. Meanwhile, invarious embodiments, the power supply control unit 520 is configured toregulate voltage and current to protect the UHF system 412 fluctuationsin power (e.g., power surge). In various embodiments, the instructionsequencer 530 may queue instructions that are directed to the memory540. In various embodiments, the memory 540 may comprise an ElectricallyErasable Programmable Read-Only Memory (EEPROM) storing data, such asinstructions from the instruction sequencer 530.

FIG. 6 is a block diagram illustrating the HF system 411 according tovarious embodiments. In various embodiments, the HF system 411 mayimplement the HF component of a dual frequency transponder, such as thetransponder 110 described with respect to FIG. 1A and the RFID storagemedium 4 described with respect to FIG. 3. As shown in FIG. 6, the HFsystem 411 operates in the 13.56 MHz band. In various embodiments, adual frequency transponder that incorporates the HF system 411 iscapable of interacting with a NFC-enabled device (e.g., Android®smartphone) when the dual frequency transponder touches, taps, or isotherwise brought within the range of the NFC-enabled device. Forexample, bringing an Android® smartphone within the range of the dualfrequency transponder activates an Android Beam™ feature on thesmartphone.

The Android Beam™ feature allows data to be transferred one NFC-enableddevice to another NFC-enabled device via NFC. For example, in someembodiments, Android Beam™ allows data to be transferred from the dualfrequency transponder to an Android® smartphone via NFC. In variousembodiments, data from the dual frequency transponder triggers thelaunch of an appropriate application on the Android® smartphone tohandle the data. In various embodiments of the systems and methodsdescribed herein, when a NFC-enabled device (e.g., Android® smartphone)reads data from a dual frequency transponder with an integrated HFcomponent (e.g., the HF system 411), an application to recharge a tollaccount launches automatically. For example, in some embodiments, dataread from the dual frequency transponder links, corresponds, orotherwise provide access to a toll account. In one common scenario, thetoll account has a deficient balance and needs to be recharged before acorresponding vehicle can pass through an ETC toll gate. In variousembodiments, the application, through integration with a virtual wallet(e.g., Google Wallet™), enables the toll account to be rechargedinstantly and on-the-spot.

As shown in FIG. 6, the HF system 411 includes a modulator 610, an AC/DCconverter 612, a codifier 614, a decoder 616, a power supply controlunit 618, an instruction sequencer 620, a security administrator 622, acryptographic block 624, and a memory 626. In various embodiments, themodulator 610 is configured to receive baseband signals from an antenna,such as the second antenna 414 (e.g., coil antenna) described withrespect to FIG. 4. In various embodiments, the AC/DC converter 612 isconfigured to receive and convert an AC signal to a DC signal.Meanwhile, in various embodiments, the codifier 614 is configured toencode the baseband signals received by the modulator 610 so that thesignals can be utilized by another device or protocol, including theinstruction sequencer 620. In various embodiments, the decoder 616 isconfigured to decode information from codifier 614 so that it may beused by another device or display. In various embodiments, theinstruction sequencer 620 is configured to queue instructions destinedfor the memory 626. In various embodiments, the security administrator622 is configured to validate the cryptographic keys sent to thecryptographic block 624. In various embodiments, one or both of thecryptographic block 624 and the memory 626 may be configured store thesecurity keys that, for example, have been validated by the securityadministrator 622 and that can be used to control (e.g., grant, deny)access to the dual frequency transponder's (e.g., the transponder 400)memory or certain content therein. Finally, in various embodiments, thepower supply control unit 618 is configured to regulate voltage andcurrent in order to protect the HF system 411 from power fluctuations(e.g., power surges).

RFID-Enabled License Plate

The various embodiments of the systems and methods described herein aredirected toward the use of a dual frequency transponder (e.g., thetransponder 110 described with respect to FIG. 1A, the RFID storagemedium 4 described with respect to FIG. 3, and the transponder 400described with respect to FIG. 4) to manage and recharge an account. Inparticular, in various embodiments, the dual frequency transponderprovides information that enables the application of both toll chargesand reloads payments to the appropriate prepaid toll account. As thedual frequency transponder may be configured to interact both with UHFRFID toll readers and with NFC-enabled devices, the dual frequencytransponder should preferably be set in a location that is convenientand accessible for scanning by both the UHF RFID toll readers and theNFC-enabled devices. Thus, according to one exemplary embodiment, it maybe desirable to attach the dual frequency transponder to a vehicleassociated with a toll account. As such, in some embodiments, the dualfrequency transponder can be a sticker (e.g., a self-adhesive decal thatcan be placed on an automobile window, windshield, or license plate), aclamshell card, or an encapsulated device (e.g., in the housing of arear-view mirror, headlights or taillights, the vehicle's front or rearbumpers, or in any non-conductive component of the vehicle).

In some embodiments, the dual frequency transponder can also be embeddedin the vehicle's license plate. However, vehicle license plates are mostcommonly made from metal (e.g., aluminum). Direct and uninsulatedcontact between a transponder (single or multi-frequency) and a metallicense plate (e.g., applying the transponder directly onto the metallicense plate) can short or severely detune the transponder's antenna(s)(e.g., the first antenna 413 and the second antenna 414 described withrespect to FIG. 4), rendering the transponder virtually unreadable.Thus, in the exemplary embodiments described in more detail below, atransponder is embedded in a metal license plate in ways that neithercompromise the performance of the transponder's antenna(s) nor addundesirable bulk to the license plate's usual dimensions. In the variousexemplary embodiments described in more detail below, a RFID-enabledlicense plate is configured to resonate at multiple frequencies (e.g.,HF and UHF bands). In some embodiments, a resonator for the transponderis formed from the license plate itself if the license plate is metal.In other embodiments, whether the plate is metal or non-metal, theresonator may be formed from a metalized layer (e.g., retro-reflectivematerial, holographic foil, or any other appropriate metallic substrate)covering the license plate.

FIG. 7A illustrates the top view of an RFID-enabled license plate 700according to various embodiments. In various embodiments, theRFID-enabled license plate 700 includes a plate 710. In variousembodiments, the RFID-enabled license plate 700 can be configured toinclude one or more slots, which are open areas that are cut or punchedout of the plate 710. In some embodiments, the RFID-enabled licenseplate 700 can be configured to include multiple slots. As shown in FIG.7A, in some embodiments, the RFID-enabled license plate 700 may includea first slot 720 and a second slot 730. In various embodiments, both thefirst slot 720 and the second slot 730 can be filled with a non-metalmaterial. In various embodiments, the non-metal material can be stuffed,extruded, or otherwise deposited into the first slot 720 and the secondslot 730. In various embodiments, the non-metal material remains flushwith respect to both the front and rear surfaces of the plate 710.

Furthermore, as shown in FIG. 7A, an RFID Strap 740 can be positionedacross the second slot 730 as illustrated. In some embodiments, the RFIDstrap 740 includes an RFID chip 742 as well as one or more contacts 744that are connected to or capacitively coupled with the plate 710. Invarious embodiments, the RFID strap 740 can include the RFID strap 740and a slot antenna formed from the plate 710. In various embodiments,the respective and relative dimensions, spacing, and location of thefirst Slot 720 and the second slot 730 are configured such that the slotantenna formed from the plate 710, the first slot 720, and the secondslot 730 will resonate at multiple desired frequencies. In variousembodiments, the slot antenna configured according to FIG. 7A is able toresonate at both a HF (e.g., 13.56 MHz) and a UHF (e.g., 915 MHz) band.As described in more detail below, in other embodiments, instead ofmultiple slots (e.g., the first slot 720 and the second slot 730 in theplate 710) configured to resonate at several different frequencies, anRFID-enabled license plate can also include a single slot configured toresonate at a single frequency.

FIG. 7B illustrates the top view of an RFID-enabled license plate 750according to various embodiments. In various embodiments, theRFID-enabled license plate 750 includes a plate 755, which may beconstructed out of a metallic material. As shown in FIG. 7B, in variousembodiments, the RFID-enabled license plate 750 can be configured toinclude a single slot 760, which may be cut or punched out of the plate755. In various embodiments, the slot 760 can be stuffed, extruded, orotherwise deposited with a non-metal material that remains flush withrespect to both the front and rear surfaces of the plate 755. In theembodiment shown in FIG. 7B, an RFID strap 770 is positioned over theslot 760. In various embodiments, the RFID strap 770 may include an RFIDchip 772 and one or more contacts 774. In various embodiments, thecontacts 774 can be connected to the plate 755 using solder, adhesivepaste, or both. In some embodiments, the contacts 774 may becapacitively coupled to the plate 755. Depending on the embodiment, theRFID strap 770 may be placed on either the front surface or the rearsurface of the plate 755. Configured according to FIG. 7B, the entireplate 755 becomes a slot antenna coupled with the RFID chip 772, whichis less sensitive to the detuning effects of a metal car frame.

FIG. 7C illustrates the top view of an RFID-enabled license plate 780according to various embodiments. In various embodiments, theRFID-enabled license plate 780 includes a plate 785 having formedthereon a slot 790, which is an open area that has been cut or punchedout of the plate 785. In some embodiments, instead of an RFID strap(e.g., the RFID strap 740 described with respect to FIG. 7A and the RFIDstrap 770 described with respect to FIG. 7B) positioned over the slot790, an RFID transponder module 792 is placed directly inside of theslot 790 as shown in FIG. 7C. In various embodiments, the RFIDtransponder module 792 may include an RFID chip 795 that is coupled witha feeding loop 797. Furthermore, as shown in FIG. 7C, in someembodiments, the slot 790 is positioned such that the feeding loop 797is capacitively coupled with the plate 785. Although not shown, in otherembodiments, the feeding loop 797 may also be inductively coupled withthe plate 785. Advantageously, the RFID transponder module 792 may bemade sufficiently thin such that even when the RFID transponder module792 is installed within the Slot 790, it creates a substantially planarsurface with respect to the plate 785.

In some embodiments, a RFID-enabled license plate can include atransponder that will not function absent a valid and properlypositioned vehicle registration sticker. For example, in someembodiments, the transponder can be intentionally tuned to a lowerfrequency (e.g., less than 915 MHz) and therefore cannot be properlyread by a UHF RFID reader. Meanwhile, in some embodiments, applying avalid vehicle registration sticker in the correct position on theRFID-enabled license plate tunes the transponder to the correct andoperational frequency (e.g., 915 MHz) so that the transponder can beread by a UHF RFID reader. In various embodiments, the vehicleregistration sticker is fabricated from or otherwise includes one ormore metallic or other conductive materials.

FIG. 8 illustrates of the top view of an RFID-enabled license plate 800according to various embodiments. In various embodiments, RFID-EnabledLicense Plate 800 includes a plate 810 and an RFID module 820. As shownin FIG. 8, the RFID-enabled license plate 800 may further include anRFID booster 830. In some embodiments, the RFID booster 830 may be aslot antenna formed from the plate 810 and one or more properly sizedand positioned slots in the plate 810. In various embodiments, the RFIDmodule 820 may be intentionally tuned to a lower, inoperable frequency.In various embodiments, a valid vehicle registration sticker 840 must beapplied in a proper location on the plate 810 in order for the RFIDmodule 820 to function properly (e.g., to be scanned or read by a UHFRFID toll reader). As will be described in more detail below, in oneexemplary embodiment, applying the vehicle registration sticker 840 inthe correct location on the RFID-enabled license plate 800 tunes theRFID module 820 to the proper frequency band.

FIG. 9 illustrates vehicle registration sticker 840 according to variousembodiments. As shown in FIG. 9, the back of the vehicle registrationsticker 840 may include a loop 910. In various embodiments, when thevehicle registration sticker 840 is affixed to an RFID-enabled licenseplate (e.g., the RFID-enabled license plate 800) in a proper location,the loop 910 may couple to an RFID transponder and tune the RFIDtransponder to a proper frequency band for operation. In otherembodiments, the vehicle registration sticker 840 may include an RFIDmodule (e.g., the RFID module 820). In those embodiments, placement ofthe vehicle registration sticker on an RFID-enabled license plate (e.g.,the RFID-enabled license plate 800) couples the vehicle registrationsticker 840 with an RFID booster (e.g., the RFID booster 830). Forexample, in some embodiments, the vehicle registration sticker 840 caninclude a single frequency (e.g., HF or NFC) transponder.

Although FIG. 8 shows that the vehicle registration sticker 840 isplaced directly over the RFID module 820, in embodiments where thevehicle registration sticker 840 is composed of or otherwise includesconductive material, the RFID module 820 may not be directly underneaththe vehicle registration sticker 840.

Typically, in the United States, motorists are required to renew theirvehicle registration on an annual basis. For example, California licenseplates have a month and a year sticker. A properly registered vehicle inCalifornia will have been issued a sticker that shows the current year.Although the registration status of a vehicle can be verified visually,in many instances, it would be preferable to verify vehicle registrationstatus through electronic and automated means. Thus, in variousembodiments, a vehicle registration sticker that is used in conjunctionwith a RFID-enabled license plate can further include or be constructedout of a material that gradually degrades as the vehicle's registrationapproaches expiration. In this manner, an up-to-date vehicleregistration sticker is able to tune a RFID transponder in theRFID-enabled license plate to the proper frequency while an expiredvehicle registration sticker cannot. Consequently, a vehicle cannotsuccessfully pass through a checkpoint unless the vehicle is alsoproperly registered and is displaying a current vehicle registrationsticker.

Vehicle registration stickers are very often made out of a metallicmaterial (e.g., retro-reflective foil). Therefore, in some embodiments,the vehicle registration sticker can be made out of a retro-reflectivematerial that degrades over time. In another embodiment, the loop on theback of the vehicle registration sticker can be made out of a materialthat degrades over time. Finally, in some embodiments, the adhesive usedto bond the vehicle registration sticker to a RFID-enabled license platecan degrade over time.

In various embodiments where a RFID-enabled license plate (e.g., theRFID-enabled license plates 700, 750, 780, and 800) comprises a dualfrequency transponder (e.g., the transponder 110, the RFID storagemedium 4, and the transponder 400), the RFID-enabled license plate maybe able to communicate with a NFC-enabled device and with a UHF RFIDreader device. In particular, in various embodiments, the RFID-enabledlicense plate is designed to be read as a vehicle passes through a tollgate. In various embodiments where the dual frequency transponder isembedded, integrated, or otherwise included in the vehicle's licenseplate, it would be preferable to install or place the toll readers inthe road, rather than in overhead gantries as in conventional ETCsystems.

FIG. 10 illustrates a reader 1000 according to various embodiments.Advantageously, placing toll readers in a configuration shown in FIG. 10may greatly reduce the cost of infrastructure associated with ETC sinceit eliminates the need to build and install gantries above the road. Invarious embodiments, the maximum height from which a transponder can beread is approximately 3.5 feet above the surface of the pavement.Meanwhile, in various embodiments, the reader 1000 may be embedded atleast 4 inches below the surface of the pavement. For variousapplications including ETC, the transponder in a RFID-enabled licenseplate may be required to include a 192-bit Tag Identification (TID)memory. As such, in various embodiments, the maximum speed at which thereader 1000 is able to successfully read a dual frequency transponderwith a 192-bit TID memory that is embedded in a license plate attachedto a passing vehicle is 140 kilometers or 87 miles per hour.

What is claimed:
 1. A system for managing an account, comprising: amulti-frequency radio frequency identification (RFID) tag configured tooperate using a first frequency band and a second frequency band; aprocessor; a non-volatile computer readable medium; a first devicecomprising a first RFID reader operating at the first frequency band andconfigured to: scan, using the first RFID reader, at least a portion ofinformation stored on the multi-frequency RFID tag; subsequent toscanning the multi-frequency RFID tag, start an application to interactwith a virtual wallet of the RFID tag, the application comprising aplurality of instructions stored on the non-volatile computer readablemedium, the plurality of instructions causing the processor to: accessthe account based at least in part on the information read from themulti-frequency RFID tag; and modify a balance associated with theaccount and the virtual wallet; and a second device comprising a secondRFID reader operating at the second frequency band and configured to:read, using the second RFID reader, at least a portion of theinformation stored on the multi-frequency RFID tag; and perform anaction related to the account based on the information read using thesecond RFID reader.